It is important to understand the flow of data through Corvus. The diagram below summarises the flow from Scada Source Systems through to Corvus.
Source Systems contain data gathered from various items of equipment relating to the operation of that equipment. These include Fleet Management Systems such as CAT Minestar, Tritronics and Modular Fleet, Dragline Monitoring systems such as Pegasys and Process Control systems such as AMPLA
xConnect SCADA System Connectors allow the transfer of Scada Source data to Corvus data formats which are standardised for each source system type. These data formats include Cycle, Activity History and Resource Event data. This data is raw data from the source system with transformations (Scada System Mappings) applied to allow mapping of Resource Names, Operator Names, Locations and Activities from the terminology used in the source system to a standardised format for consistent reporting in Corvus
Business Rules are then applied to this raw data to consolidate it to Process Activity data recorded at the shift level. These are a set of rules of which allows the business to view the data in forms or which are most applicable
Process Activities module displays all data (both Production and Time for the Activity) may be recorded directly against a process activity, which is based on the business rules of the activity. Data automatically refreshes into Corvus Process Activities module as often as it becomes available from the Source system. Data can also be manually entered if required
Export Mappings allow Process Activity data to be transformed for export to other systems such as ERP and external reporting system
Timing of Data Transfer, the transfer of data from Scada Source Systems via xConnect Connectors occurs:
On a regular schedule during the current shift. The frequency of these transfer depends on the capability of the source system to supply the required data, but they typically occur every 1 to 2 minutes
After the completion of each shift a further transfer is done for the prior shift in order to transfer any source system data that was captured at the source system after the completion of the shift
By operator action for previous shifts using the External Source System option in Axiom
